Skip to content

Conversation

@timbl
Copy link
Contributor

@timbl timbl commented Jun 2, 2019

Closes #1211.
Closes #1212.

Copy link
Contributor

@RubenVerborgh RubenVerborgh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got some nits; will fix them myself.

@RubenVerborgh RubenVerborgh self-assigned this Jun 2, 2019
@RubenVerborgh RubenVerborgh force-pushed the getFilePath branch 2 times, most recently from 4bffc6b to f4cba19 Compare June 2, 2019 20:08
@RubenVerborgh RubenVerborgh changed the title Tweak put.js to avoid problem with URIs with spaces in Restrict knowledge of the URL/file mapping again to ResourceMapper Jun 2, 2019
@RubenVerborgh RubenVerborgh assigned megoth and unassigned RubenVerborgh Jun 2, 2019
@RubenVerborgh RubenVerborgh requested review from kjetilk and megoth June 2, 2019 21:07
@RubenVerborgh
Copy link
Contributor

@megoth Too much knowledge about the URL/file mapping was leaking in other components, leading to bugs such as #1211, which #643 was created to prevent.

Unit tests run, but have not checked anything else. In particular, you want to look at:

  • allow.js
  • globbing (which now no longer is a hack, but has been reduced in functionality to only folder globs)
  • a skipped test which I think was incorrect

Copy link
Contributor

@megoth megoth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a lot happening here, but AFAICT it looks good ^_^

@kjetilk
Copy link
Member

kjetilk commented Jun 6, 2019

@RubenVerborgh perhaps you can hit merge on this when you're happy?

@RubenVerborgh RubenVerborgh merged commit 111e63b into master Jun 7, 2019
@RubenVerborgh RubenVerborgh deleted the getFilePath branch June 7, 2019 08:22
@RubenVerborgh
Copy link
Contributor

Thanks all!

@michielbdejong
Copy link
Member

@RubenVerborgh so did #1226 start happening when this PR was merged, or was that a coincidence?

@RubenVerborgh
Copy link
Contributor

Yes; some of the knowledge that needed to be inside of ResourceMapper was encoded externally, and in a different way. Relying again on ResourceMapper brought to light the incorrect mapping.

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

Labels

Projects

None yet

6 participants