ba-web-framework

Author	SHA1	Message	Date
Alan Bridgeman	b5f7c028e2	Trying explicitly throwing error to trigger catch clause All checks were successful Publish to Private NPM Registry / publish (push) Successful in 31s Details	2025-06-24 13:59:14 -05:00
Alan Bridgeman	b357cf3f8f	Added more stuff for debugging to figure out what is happening All checks were successful Publish to Private NPM Registry / publish (push) Successful in 30s Details	2025-06-24 13:37:18 -05:00
Alan Bridgeman	9a073f6dca	A workaround (maybe) for a really annoying issue with error handling and how parameters get passed to what All checks were successful Publish to Private NPM Registry / publish (push) Successful in 33s Details	2025-06-24 12:19:45 -05:00
Alan Bridgeman	711007a67a	Forgot to change code in second spot (this is why DRY principal exists etc...) All checks were successful Publish to Private NPM Registry / publish (push) Successful in 43s Details	2025-06-24 11:59:15 -05:00
Alan Bridgeman	203d0488e6	Because for async contexts the All checks were successful Publish to Private NPM Registry / publish (push) Successful in 42s Details ext function still seems to be undefined within the #Page decorator we just reject the Promise instead hoping this will tigger the proper express Error handling	2025-06-24 11:42:01 -05:00
Alan Bridgeman	0305f5eaeb	Attempting to handle async properly under this new wrapping strategy in the hope that makes both async and normal functions act consistently All checks were successful Publish to Private NPM Registry / publish (push) Successful in 43s Details	2025-06-24 11:12:42 -05:00
Alan Bridgeman	33511adf1c	Reverting back from pp.use to pp.get but adding some debugging to see if I can find a path forward All checks were successful Publish to Private NPM Registry / publish (push) Successful in 39s Details	2025-06-24 09:15:16 -05:00
Alan Bridgeman	73c2c404cf	Added return to see if that stops timed out error All checks were successful Publish to Private NPM Registry / publish (push) Successful in 32s Details	2025-06-24 08:53:26 -05:00
Alan Bridgeman	338e67e4d2	Seeing if by using pp.use instead of pp.get I get the next function as expected that would allow for proper error handling withn the decorators All checks were successful Publish to Private NPM Registry / publish (push) Successful in 43s Details	2025-06-24 08:27:25 -05:00
Alan Bridgeman	ecb9a27d8d	Seemingly accidentally ended up with an infinite loop.Hopefullly this fixes it All checks were successful Publish to Private NPM Registry / publish (push) Successful in 43s Details	2025-06-24 07:41:39 -05:00
Alan Bridgeman	868a8aaadb	Attempting change to Controller's setup to see if it fixes error handling problem All checks were successful Publish to Private NPM Registry / publish (push) Successful in 43s Details	2025-06-24 07:22:34 -05:00
Alan Bridgeman	e3ba1639c4	Even More Debugging All checks were successful Publish to Private NPM Registry / publish (push) Successful in 46s Details	2025-06-24 06:46:40 -05:00
Alan Bridgeman	eb7dcaf556	More Debugging All checks were successful Publish to Private NPM Registry / publish (push) Successful in 33s Details	2025-06-23 20:24:20 -05:00
Alan Bridgeman	d8e8c3bbcd	Debugging All checks were successful Publish to Private NPM Registry / publish (push) Successful in 49s Details	2025-06-23 19:42:53 -05:00
Alan Bridgeman	a308d69766	Attempted to add proper error handling within the Page decorator such that errors are handled consistently both with and without the Page decorator All checks were successful Publish to Private NPM Registry / publish (push) Successful in 55s Details	2025-06-23 16:46:40 -05:00
Alan Bridgeman	332e177f99	Bringing local and remote repository in line with one another again	2025-04-30 14:58:07 -05:00
Alan Bridgeman	74997cb676	Bringing local and remote repository in line with one another and adding Github Actions to publish package	2025-04-29 12:06:39 -05:00
Alan Bridgeman	28db152b87	Initial Code Commit	2025-02-17 16:32:27 -06:00

18 commits