hazaar/hazaar-warlock
1
0
Fork 0
Code Issues Pull requests 2 Projects Releases 4 Packages Wiki Activity Actions

Remove dependency on Hazaar MVC versions #50

New issue
Closed
opened 2019-05-28 01:14:44 +00:00 by jamie · 6 comments
jamie commented 2019-05-28 01:14:44 +00:00 (Migrated from git.hazaar.io)
Copy link

Right now, Hazaar MVC core is responsible for starting up application services and containers for running code. This means that if I make changes to way things starts up, then they are tied in with a specific version of Hazaar MVC core. I'd like to look into finding a way to reduce the code execution in core to as little as possible and finding a generic way to take input from STDIN and process it in Hazaar Warlock code only. This means that going forward from MVC 3.0 and Warlock 3.0 they will be more version independent of each other.

Right now, Hazaar MVC core is responsible for starting up application services and containers for running code. This means that if I make changes to way things starts up, then they are tied in with a specific version of Hazaar MVC core. I'd like to look into finding a way to reduce the code execution in core to as little as possible and finding a generic way to take input from STDIN and process it in Hazaar Warlock code only. This means that going forward from MVC 3.0 and Warlock 3.0 they will be more version independent of each other.
jamie commented 2019-05-28 01:15:27 +00:00 (Migrated from git.hazaar.io)
Copy link

changed the description

changed the description
jamie commented 2019-05-28 01:15:36 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in merge request !22

mentioned in merge request !22
jamie commented 2019-05-28 01:15:36 +00:00 (Migrated from git.hazaar.io)
Copy link

created merge request !22 to address this issue

created merge request !22 to address this issue
jamie commented 2019-05-28 02:13:32 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via merge request !22

closed via merge request !22
jamie commented 2019-05-28 02:13:32 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit 5079482a799cf89e9c77f6911a0cf609afb2a049

mentioned in commit 5079482a799cf89e9c77f6911a0cf609afb2a049
jamie commented 2020-04-14 23:30:33 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit 90bda0b745

mentioned in commit 90bda0b745ef516d2df6929a2a088bda3497f7e2
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
3.0-develop
58-restful-triggers
2.2-stable
2-warlock-to-warlock-communication
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.5
release-2.1.4
release-2.1.3
release-2.1.2
release-2.1.1
release-2.1.0
release-2.0.2
release-2.0.1
release-2.0.0
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
release-0.4.0
release-0.3.0
release-0.2.0
release-0.1.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#50
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?