You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is something confusing with the way we store the url and anchor.
The scraper index both a anchor field and a url one, but the url already contains the anchor. We do that because we're doing a distinct on the url. But the JS client also concatenate the url and anchor, which results in weird things.
I think we should:
Remove the anchor field from the scraper
Remove the concatenation from the JS client
The text was updated successfully, but these errors were encountered:
<a name="1.0.2"></a>
## [1.0.2](v1.0.1...v1.0.2) (2015-12-28)
### Bug Fixes
* **debut:** do not enable debug by default ([188f49e](188f49e))
* **url:** Removes concatenation of URL with hash if it contains a hash ([348df1c](348df1c)), closes [#53](#53)
* **usage:** fixed usage to match the latest prototype version ([f6edc9e](f6edc9e))
There is something confusing with the way we store the
url
andanchor
.The scraper index both a
anchor
field and aurl
one, but theurl
already contains the anchor. We do that because we're doing adistinct
on theurl
. But the JS client also concatenate theurl
andanchor
, which results in weird things.I think we should:
anchor
field from the scraperThe text was updated successfully, but these errors were encountered: