Skip to content

Conversation

@ujjwalt
Copy link
Owner

@ujjwalt ujjwalt commented Jul 3, 2014

We try to factor out common methods for a scope into the AbstractScope class.
It is yet unclear whether the Scope class should inherit from AbstractScope or if AbstractScope in itself suffices. This will only get clear when we start implementing resources. Right now we're trying to create an object graph which can generate non resourceful routes and is divided into small understandable files

\cc @pixeltrix

ujjwalt added 3 commits July 4, 2014 04:29
Change path normalization methods to class methods
Use set accessor to access the set
Return an empty hash for hash based scope properties if they are not supplied
@ujjwalt
Copy link
Owner Author

ujjwalt commented Jul 4, 2014

I guess once we're happy with the file and code organization and the classes and their hierarchy, I'll start work on improving performance.

@ujjwalt
Copy link
Owner Author

ujjwalt commented Aug 13, 2014

@pixeltrix Switched to a module for AbstractScope. We have few days left. I'll finish this off but you'll have to constantly interacting here for me to be able to do this quickly. I still haven't heard back from you regarding the priority of the supplied path and path option

A bug in prefix_name_for_action prevented from proper route helper
generation
Added default_url_options
Fixed processing of to option and added root method
Append '/' only if child module exists along with parent module
Added has_named_route? method
Added some outline to match_route but we’ll leave that aside for the
time being and replace the implementation in future after we get the
whole thing working
It declares routes for a simple resource :single_resource declaration
This needs to be a separate class. Need to rethink resources
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants