Skip to content

Wire up LegacyResourceMapper #661

Closed
Closed

Description

@RubenVerborgh

The LegacyResourceMapper introduced in #660 should replace all inline URL to filename (and vice-versa) mapping, so we:

  • provide consistent mapping behavior all over, and eliminate bugs in existing mapping code (or at least confine those bugs to one place)
  • simplify the transition to the new ResourceMapper (Wire up ResourceMapper #662)

Activity

  1. added this to the 4.1.0 milestone on May 3, 2018
  2. RubenVerborgh commented on May 3, 2018

    @RubenVerborgh
    ContributorAuthor

    We possibly might want to do this by changing the interface of ldp, such that it accepts URLs rather than filenames. Then, ldp itself can call LegacyResourceMapper instead of requiring all of its callers to do that.

  3. modified the milestones: 4.1.0, 5.0.0 on Jul 19, 2018
  4. RubenVerborgh commented on Aug 21, 2018

    @RubenVerborgh
    ContributorAuthor
  5. self-assigned this
    on Nov 13, 2018
  6. rubensworks commented on Nov 14, 2018

    @rubensworks
    Contributor

    Ok, I'm working on this issue now.

    I'm still relatively new to the codebase, so I could use some input on where I could find calls that should be changed.
    So far, I see the following:

    I assume there may be others as well?

  7. RubenVerborgh commented on Nov 14, 2018

    @RubenVerborgh
    ContributorAuthor
  8. megoth commented on Nov 14, 2018

    @megoth
    Contributor

    @rubensworks if you're going to edit lib/utils.js, maybe it's a good time those functions to a utility-file in lib/common? Trying to make methods a bit more reusable by putting them in more explicitly named utility-files.

  9. rubensworks commented on Nov 14, 2018

    @rubensworks
    Contributor

    @megoth The plan is actually to remove as much as possible from lib/utils.js :-) In favor of the new methods of ResourceMapper.

    But the remaining functions could indeed be moved to lib/common afterwards.

  10. kjetilk commented on Nov 14, 2018

    @kjetilk
    Member

    Note that there is stuff in the #911 that is in lib/utils.js too, and it would be nice to avoid conflicts. Not sure we should do that now, perhaps post-5.0.0 if needed?

  11. rubensworks commented on Nov 14, 2018

    @rubensworks
    Contributor

    I assume #911 will be merged before this refactor is done, so I'll have to rebase in any case.

  12. rubensworks commented on Nov 20, 2018

    @rubensworks
    Contributor

    Done in #952.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions